Skip to content

📝 Add Board Affiliation and Co-Affiliation limits (4.9 and 4.10) #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 10, 2025

Conversation

jefftriplett
Copy link
Member

@jefftriplett jefftriplett commented Apr 10, 2025

Fixes #4

For any members who are interested in the Forum thread: https://forum.djangoproject.com/t/dsf-bylaws-are-now-on-github/40262

Verified

This commit was signed with the committer’s verified signature.
jefftriplett Jeff Triplett
Fixes #4
@jefftriplett jefftriplett changed the title 📝 Add board affiliation and limit rules to bylaws 📝 Add Board Affiliation and Co-Affiliation limits (4.9 and 4.10) Apr 10, 2025
@jefftriplett jefftriplett requested a review from a team April 10, 2025 14:23
Comment on lines +117 to +121
(a) is an employee, officer, or member of the Board of Directors of another entity;

(b) maintains a significant consulting relationship with another entity; or

(c) owns at least 1% of the equity or debt, or derivatives thereof, of another entity.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
(a) is an employee, officer, or member of the Board of Directors of another entity;
(b) maintains a significant consulting relationship with another entity; or
(c) owns at least 1% of the equity or debt, or derivatives thereof, of another entity.
1. is an employee, officer, or member of the Board of Directors of another entity
2. maintains a significant consulting relationship with another entity; or
3. owns at least 1% of the equity or debt, or derivatives thereof, of another entity.

Is it possible for us to use more accessible formatting for this as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine to do, but I'm going to leave it open, in case there's a legal(ease) reason that I'm not aware of for why we should keep it.

(noting this mostly to myself, but we should probably preview it in case we need to indent the bullets since our overall doc structure is weird to being with)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should do this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to close this because it breaks the format we have with sub-sections (maybe sub-sub-sections) and it looks weird.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not going to die on this hill but I don’t understand your points Jeff so I’d like to revisit this? Creating lists in content without using semantic lists markup is an accessibility own goal. I don’t think it would prevent anyone from understanding the content but it’s probably something I would fail an accessibility audit for if I was auditing (WCAG SC 1.3.1 Info and Relationships

@thibaudcolas thibaudcolas requested a review from a team April 11, 2025 05:25
jefftriplett and others added 2 commits April 11, 2025 08:01

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
Copy link
Member

@knyghty knyghty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@knyghty
Copy link
Member

knyghty commented Jul 9, 2025

This looks all good to me if we can resolve the remaining open comments.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@jefftriplett
Copy link
Member Author

This just passed by the board.

@jefftriplett jefftriplett merged commit d3f964f into main Jul 10, 2025
@jefftriplett jefftriplett deleted the 4-affiliations-and-co-affiliations branch July 10, 2025 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Affiliations of Board Members
7 participants